Pod operating system for a vertical take-off and landing (VTOL) unmanned aerial vehicle (UAV)

ABSTRACT

A vertical take-off and landing (VTOL) unmanned aerial vehicle (UAV) storage and launch system includes a UAV pod having a UAV pod processor and a UAV selectively enclosed in the UAV pod, the UAV having only two rotors.

CROSS-REFERENCE TO RELATED APPLICATIONS

This application claims priority to and the benefit of U.S. Provisional Patent Application Ser. No. 62/115,029 filed Feb. 11, 2015, which is hereby incorporated herein by reference in its entirety for all purposes.

BACKGROUND

Field of the Invention

The field of the invention relates to unmanned aerial vehicle (UAV) systems, and more particularly to systems for operating a UAV autonomously.

Description of the Related Art

Aerial geographic survey work for the agricultural and oil industries incur the logistics and costs of personnel to operate and maintain the air vehicle as well as collect and process the associated data. These costs are typically compounded by need for a substantial amount of this work to be performed at, or relatively near to, the location of the survey, which typically is well removed from any population centers. As a result it is advantageous to increase automation, reliability (reduce complexity), range, and capability of an air vehicle and support system for performing such data retrieval and processing tasks.

SUMMARY

A vertical take-off and landing (VTOL) unmanned aerial vehicle (UAV) storage and launch system may include a UAV pod having a UAV pod processor, and a UAV selectively enclosed in the UAV pod, the UAV having only two rotors. The system may include a display on the UAV pod and/or a rearward facing tang extending from a rear fuselage portion of the UAV.

Another unmanned aerial vehicle (UAV) storage and launch system is disclosed that includes a UAV pod having a UAV pod processor and short-range UAV pod transceiver, a vertical takeoff and landing (VTOL) two-rotor UAV enclosed in the UAV pod, the two-rotor UAV having a UAV processor and a UAV transceiver, the UAV processor in communication with the UAV pod processor through the short-range UAV pod transceiver and the UAV transceiver. The UAV pod processor may be configured to provide mission instructions to the UAV processor and to monitor UAV trajectory information. The system may also include a proximity sensor coupled to the UAV pod, with the proximity sensor configured to detect the presence of an object positioned over the UAV pod, when an object is present. A weather sensor may also be included that is in communication with the UAV pod processor, and a UAV pod memory may be in communication with the UAV pod processor. In some configurations, the UAV pod memory is portable memory, such as a secure digital (SD) card, and the system may include a long-range UAV pod transceiver coupled to the UAV pod and in communication with the UAV pod processor, with the UAV pod processor further configured to monitor UAV pod external environmental conditions in response to information received from the weather sensor. The UAV pod processor may be further configured to provide reroute instructions to the two-rotor UAV, and the rerouting instructions may include instructions to return to the UAV pod for landing. In preferred embodiments a UAV pod cover is included that is operable to open and close.

A method of unmanned aerial vehicle (UAV) launch and control may include transmitting one of a plurality of missions to a two-rotor UAV seated in a UAV pod, launching the two-rotor UAV out of the UAV pod, monitoring a trajectory of the two-rotor UAV using a UAV pod transceiver in communication with a UAV pod processor, the UAV pod processor coupled to the UAV pod, and monitoring a battery status of the two-rotor UAV during flight. The method may also include providing re-routing instructions to the two-rotor UAV from the UAV pod and the re-routing instructions may include UAV instructions to return to the UAV pod for landing. In certain embodiments, the method may also include downloading geographic survey data from the two-rotor UAV to a UAV pod memory in communication with the UAV processor, and the UAV pod memory may be portable memory detachably connected to the UAV pod. In other embodiments, the method may include landing the two-rotor UAVs in the UAV pod, closing a UAV pod protective cover over the two-rotor UAV, downloading geographic survey data from the two-rotor UAV to a UAV pod memory in communication with the UAV processor, transmitting another one of a plurality of missions to the two-rotor UAV seated in the UAV pod, opening the protective cover, and launching the two-rotor UAV out of the UAV pod. The launch and control method may also include monitoring for overhead obstacles using a proximity sensor, monitoring the weather using a weather sensor, and transmitting the geographic survey data to an operations center disposed remote from the UAV pod.

Another unmanned aerial vehicle (UAV) storage and launch system may include a UAV pod processor and a UAV pod transceiver in communication with the UAV pod processor, the UAV pod processor configured to monitor a predetermined two-rotor UAV, when the two-rotor UAV is present, a two-rotor UAV trajectory, and a UAV battery status; and a UAV pod memory in communication with the UAV pod processor, the UAV pod memory storing a plurality of UAV missions that collectively provide a geographic survey of an area.

BRIEF DESCRIPTION OF DRAWINGS

The components in the figures are not necessarily to scale, emphasis instead being placed upon illustrating the principals of the invention. Like reference numerals designate corresponding parts throughout the different views. Embodiments are illustrated by way of example and not limitation in the figures of the accompanying drawings, in which:

FIG. 1 is a perspective view of one embodiment of a UAV pod that may house and protect an extended range VTOL UAV to accomplish multiple autonomous launches, landings and data retrieval missions;

FIG. 2 is a perspective view of the two-rotor UAV first illustrated in FIG. 1;

FIGS. 3A and 3B illustrate the UAV pod in its open and closed configurations, respectively;

FIG. 4 is a data flow diagram illustrating information flow from a customer requesting data to a customer support center, an operational support center, a UAV in a UAV pod, and pod-processed data being provided to the customer support center after each flight mission;

FIG. 5 is a data flow diagram illustrating another embodiment of the flow of information from a customer requesting data to a customer support center, to an operational support center, to a UAV in a UAV pod, and pod-processed missions data being provided to the customer support center after all flight missions have been completed;

FIG. 6 is a flow diagram illustrating one embodiment of use of the UAV pod and UAV system by a customer in accordance with FIG. 4 and embodiments for migrating the UAV to another geographic area;

FIG. 7 illustrates flight of the UAV 701 from its pod to within range of a wireless connection such as that provided by wireless local area network standard IEEE 802.11x (“Wi-Fi”) connection, such as might be provided in a residential house, for transmission of missions data;

FIG. 8 is a flow diagram illustrating one embodiment of a method of conducting flight missions for the UAV;

FIG. 9 is a block diagram illustrating the use of a plurality of UAV pods with only one UAV to extend the possible geographic survey area from what would otherwise exist with only one UAV;

FIG. 10 is a UAV pod and associated UAV provided with a plurality of missions that cover a rectangular coverage area; and

FIG. 11 illustrates two extended coverage survey areas that may be serviced using only one UAV or a limited number of UAVs.

DETAILED DESCRIPTION

A vertical takeoff and landing (VTOL) unmanned aerial vehicle (UAV) system is disclosed that provides for improved remote geographic survey capabilities. Multiple autonomous mission launches and landings may be accomplished using a two-rotor VTOL UAV that is capable of efficient horizontal flight, and a UAV pod having a UAV pod processor, with the UAV selectively enclosed in the UAV pod for protection against the external environment when not in use, recharging and/or transferring data.

More particularly, a UAV pod is described that has a UAV pod processor and a short-range UAV pod transceiver. A VTOL UAV may be stored in the UAV pod prior to launch, and the UAV may have a UAV processor and a UAV transceiver. The UAV pod processor may communicate with the UAV processor via their respective transceivers, and the UAV pod may provide the UAV with mission instructions. After launch of the UAV, the UAV pod processor may monitor the UAV trajectory and battery status.

Exemplary UAV Pod and UAV Structure

FIG. 1 is a perspective view of one embodiment of a UAV pod that may house and protect an extended range VTOL UAV to accomplish multiple autonomous launches, landings and data retrieval missions. The illustrated system 100 may have a winged two rotor UAV 102 seated on a landing surface 104 of an interior 106 of the UAV pod 108. The UAV 102 may be seated or otherwise maneuvered to a vertical launch position to facilitate later launch out of the UAV pod 108. The UAV pod 108 may selectively enclose the UAV 102, such as through the use of a UAV pod protective cover 110. The cover 110 may be a hinged cover, such as a two-part hinged cover, that is operable to close to protect the UAV 102 from the external environment or to open to enable launch of the UAV 102. The UAV pod 108 may have a short-range UAV pod transceiver 112 that may be seated in a compartment below the landing surface 104, within their own separate compartments, or may be seated elsewhere within the UAV pod 108 for protection from the external environment. The UAV pod transceiver 112 may receive UAV flight telemetry such as UAV flight and trajectory information, UAV battery status information and sensor data (such as video), and other data transmitted by the UAV 102. The UAV pod transceiver 112 may also transmit flight control data such as navigation (e.g., re-routing instructions) to the UAV 102. A UAV pod processor 114 may also be housed within the UAV pod 108 to accomplish, among other functions, providing the UAV 102 with a plurality of missions, receiving flight survey data from the UAV 102, monitoring the UAV pod 108 for overhead obstacles, monitoring the external environment such as the weather through the weather sensor, monitoring the trajectory of the UAV 102, and providing navigation instructions to the UAV 102 in response to receiving UAV battery status or other flight warning condition data inputs.

A UAV pod memory 116 may also be housed within the UAV pod 108 for storing UAV flight mission information and geographic survey data. A battery 118 may be enclosed in the UAV pod for recharging the UAV 102 and for providing power to the UAV pod 108 such as for use by the processor 114 and cover motor (not shown). The battery 118 may be rechargeable such as through solar panels 119, or may be a permanent battery such as a 12-Volt deep cycle marine battery. In an alternative embodiment, the battery 118 may be a fuel cell. In some embodiments, the UAV pod 108 will use the solar panels 119 to charge the battery 118 to later charge the battery of the UAV 102. Typically, the UAV pod 108 will be charging the battery 118 while the UAV 102 is out of the pod 108 executing a mission and will recharge the UAV 102 upon its return to the UAV pod 108.

A weather sensor 120 in communication with the UAV pod processor 114 may extend from an exterior of the UAV pod 108 to enable accurate measurement of the external environment, such as wind speed, temperature and barometric pressure. A proximity sensor or sensors may also be provided (122, 124) and in communication with the UAV pod processor 114 to enable go and no-go flight decisions based on the proximity of any objects or other obstructions positioned over the UAV pod cover 110. The UAV pod 108 is preferably weather hardened to enable extended outdoor use regardless of weather variations.

FIG. 2 is a perspective view of the two-rotor UAV 102 first illustrated in FIG. 1. The UAV 102 has only two rotors 202, enabling vertical takeoff and landing (VTOL) missions out of the UAV pod 108 (see FIG. 1) and efficient horizontal flight. The UAV 102 has a UAV transceiver 204 within a UAV fuselage 206. A UAV processor 208 is also seated in the UAV 102 and in communication with the UAV transceiver 204. The UAV 102 also includes a battery 209 for providing power to the rotor motors and the electronics, including the processor 208. The UAV processor 208 is configured to receive a plurality of flight mission instructions and other information that may include waypoints, altitude, flight speed, sensor suite configuration data, launch day/time and mission weather sensor go and no-go parameters. The UAV 102 may have a variety of electrical optical (EO) sensors 210, such as LiDAR, RADAR, infrared, visible-spectrum cameras, or other active or passive sensors that may be used to detect soil moisture, crop density, crop health, terrain, or other objects or qualities of interest. The UAV 102 may have a rear landing gear 212 extending off of a rear of the fuselage 206 that may be used in combination with UAV engine nacelles 214 to enable a four-point landing for more stable landings on the UAV pod 108 (see FIG. 1). The landing gear 212 may also function as a flight surface or aerodynamic surface, such as a vertical stabilizer, providing corrective (passive) forces to stabilize the UAV 102 in flight, such as to stabilize in a yaw direction. The UAV 102 may have wings 215 to provide the primary source of lift during the UAV cruise (e.g., horizontal flight), while the two rotors 202 provide the primary source of lift during the VTOL phases of UAV flight. This combination of wing and rotor use allows for efficient flight while collecting flight survey data, which increases the range and/or duration of a particular flight while also allowing the UAV 102 to land and take off from the relatively small UAV pod 108 (see FIG. 1) landing area. In one embodiment, the UAV 102 may take off and land vertically using the two rotors 202 that themselves are operable to lift the UAV 102 vertically upwards, transition the UAV 102 to horizontal flight to conduct its survey or other flight mission, and then transition it back to vertical flight to land the UAV 102 vertically downwards, with attitudinal control for the UAV 102 in all modes of flight (vertical and horizontal) coming entirely from the rotors 202 (as driven by a means of propulsion) without the benefit or need of aerodynamic control surfaces, such as ailerons, an elevator, or a rudder. One such UAV 102 is described in international patent application number PCT/US14/36863 filed May 5, 2014, entitled “Vertical Takeoff and Landing (VTOL) Air Vehicle” and is incorporated by reference in its entirety herein for all purposes. Such a UAV 102 benefits from a more robust structure by reducing the opportunity for damage to control surfaces (i.e., there aren't any), and may be made lighter and with less complexity.

The UAV 102 may also be provided with a rearward facing tang 216 extending off of a rear portion 218 of the fuselage 206 in lieu of or in addition to rear landing gear 212. Such rearward-facing tang 216 may be metallic or have metallic contacts (electrical contacts) for receipt of electrical signals (i.e., data) to be communicated to the UAV processor and/or power for charging the UAV's battery 209.

FIGS. 3A and 3B illustrate the UAV pod 108 in its open and closed configurations, respectively. In FIG. 3A, the UAV 102 is illustrated in its vertical configuration and seated on a landing surface 104 of the UAV pod 108. The UAV 102 is shown positioned at least generally aligned with the rectangular dimensions of the UAV pod 108. In embodiments, the landing surface 104 is rotatable to position the UAV. In FIG. 3A, the cover 110 is open to enable unobstructed launch, and later landing, of the UAV 102. The cover 110 is illustrated with side portions 300 and top portions 302, with hinges 304. In an alternative embodiment, only the top portions 302 are hinged to enable unobstructed launch of the UAV 102. Alternatively, the top portions 302 may translate out of the flight path linearly or using a mechanism and motion so that the UAV is free to launch. In one embodiment, the landing gear 212 may be omitted and the UAV 102 may be guided into and out of one or more slots, guide rails, channels, or other guiding structure to both secure the UAV 102 during its landed state and enable landing. The weather sensor 120 may be coupled to the cover 110 or may extend off the side of the UAV pod 108 (not shown). Also, although the UAV pod 108 is illustrated having a rectangular cross-section and a box-like structure, the UAV pod 108 may take the form of a dome-shaped structure or other configuration that enables stable placement and protection for the selectively enclosed UAV. The cover 110 can include solar panels on its exterior (not shown), and in some embodiments, one or both of the covers 110 can be positioned, and moved, about the hinges 304 to be perpendicular to the sun's rays to maximize the collection of solar energy. In other embodiments, the short-range UAV pod transceiver 112 may also have features of or include a long-range UAV pod transceiver 113 for communication with a cellular tower.

Business Methods of Operation

FIG. 4 is a data flow diagram illustrating information flow from a customer requesting data to a customer support center, an operational support center, a UAV in a UAV pod, and back again. A customer may submit a data request 400, such as a request for a geographic aerial survey, to a customer support center. The customer support center may work with the customer and the received data to finalize the data request for transmission 402 to an operational support center. The operational support center may use the finalized data request to determine the location of a launch site in or adjacent to a UAV pod survey site, to plan a plurality of flight missions that collectively accomplish the customer's geographic survey data request. The resultant missions plan data may then be provided 404 to a UAV pod that may be deployed to the launch site. Prior to launch, the first of the plurality of missions is provided to the UAV 406 in the form of flight data, such as altitude, heading, and way points, and the UAV is launched to perform the mission. Upon return of the UAV to the UAV pod, the survey raw data, such as camera imagery, event logs, GPS and IMU raw data, may be provided 408 to the UAV pod. In one embodiment, the UAV pod may pre-process the data, such as by converting the raw data into viewable JPGs with an accompanying geospatial location. Additional pre-processing may be performed, such as stitching the images into an orthomosaic. In a further embodiment, such pre-processing may be performed onboard the UAV prior to providing the data to the UAV pod. The pre-processed data may be provided 410 to the customer support center for final processing.

The next mission's flight data may be provided 412 to the UAV and the UAV may be launched to perform the next survey mission. Upon its return, the survey raw data may be provided 414 to the UAV pod for pre-processing and the pre-processed data may then be provided 416 to the customer support center for additional processing. With the UAV receiving the last mission flight data 418 and upon receipt by the UAV pod of the final survey raw data 420, the final pod-processed data may be provided 422 to the customer support center. After final processing of the collective missions pre-processed data, the survey results may be provided 424 by the customer support center to the customer.

FIG. 5 is a data flow diagram illustrating another embodiment of the flow of information from a customer requesting data to a customer support center, to an operational support center, to a UAV in a UAV pod, and back again to the customer. As illustrated above, the customer may submit the data request 500 to the customer support center that may then finalize the data request for transmission 502 to an Operational Support Center. The processed requested data is used to develop a plurality of flight missions that collectively accomplish the customer's data request. The resultant missions plan data may then be provided 504 to the UAV pod that may be deployed to the launch site, and the first mission's flight data may be provided 506 to the UAV prior to launch and accomplishment of the first flight survey mission. The pre-processed survey data may be provided 508 to the UAV pod for storage, and the second mission's flight data provided 510 to the UAV to conduct the second mission's survey. Upon returning to the UAV pod, the second mission's pre-processed flight data may be provided 512 to the UAV pod. After the last mission's flight data is provided 514 to the UAV by the UAV pod and after conclusion of the last flight mission survey, the last mission's flight survey data may be provided 516 to the UAV pod and the collective missions' pod-processed survey data provided 518 to the customer support center for final processing before providing 520 the finally-processed survey data to the customer.

FIG. 6 is a flow diagram illustrating one embodiment of use of the UAV pod and UAV system by a customer. A first data request is received from a customer, such as an owner of an agricultural field or land use manager (block 600). The customer may input the data request through a website portal that requests information detailing the request. For example, the customer may wish to provide geographic boundaries to survey a first geographic coverage area during a specific period of time to accomplish a refresh rate. “Refresh rate” refers to the number of times each area of the geographic coverage area is imaged during the deployment period for that geographic coverage area. In other embodiments, the data request may include a ground resolution or ground surface distance (“GSD”). For example, a GSD of one inch may enable the coverage areas and refresh rates described in Table 1.

TABLE 1 Example 1 Example 2 Example 3 UAV Deployment 90 days 90 days 90 days Period UAV Missions 360 360 360 GSD 1 inch 1 inch 1 inch Coverage Area 100,000 12,500 6,250 Refresh Rate 1 (once/90 days) 8 (once/11 days) 16 (once/6 days)

Similarly, by suitably modifying GDS values, the UAV may have the coverage area and refresh rates listed in Table 2.

TABLE 2 Example 4 Example 5 Example 6 Example 7 UAV Deployment 90 days 90 days 90 days 90 days Period UAV Missions 360 360 360 360 GSD 2 inch 4 inch 0.5 inch 0.25 inch Coverage Area 100,000 12,500 50,000 25,000 (acres) Refresh Rate 2 (once/45 days) 4 (once/23 days) 1 (once/90 days) 1 (once/90 days)

In other embodiments, rather than inputting the data request through a website portal, the customer may provide the data through a proprietary software interface or via a telephone interview mechanism, each in communication with a customer support center. A plurality of flight missions may then be planned that collectively accomplish the customer's (block 602) request such as by pre-planning how many flights and from what general areas they need to operate. The planned flight missions, such flight missions including flight mission data representing takeoff day/time, waypoints, flight altitudes, flight speeds, and such, are provided to the UAV pod (block 604) for future communication to a UAV seated in the UAV pod.

The UAV pod may then be deployed to a launch site that is either within or adjacent to the customer-desired geographic coverage area (block 606). Deployment may consist of loading the UAV into a UAV pod and transporting both to the launch site by means of truck or aircraft transport. By way of further example, the UAV pod and enclosed UAV may be transported by a commercial carrier (e.g., FedEX, UPS, etc.) to a farm for offloading into a field, or by an oil and gas utility company to a location adjacent a transmission or pipeline that may be the subject of a visual survey. The UAV may be provided with flight mission data representing one of the plurality of missions (block 608) such as by short range wireless or wired communication within the UAV pod. As used herein, “short range” may be defined as a range having sufficient distance to communicate with the UAV throughout the UAV's maximum range of flight. The UAV may then be launched out of the UAV pod to perform the provided flight mission (block 610). As described herein, a “mission” or “flight mission” preferably encompasses one launch, survey flight, and landing, but may encompass more than one launch/flight/landing. The flight mission data may also include dynamic flight instructions, such as altering its trajectory, attitude or such as by dropping a payload if certain conditions exist, such as would be valuable in a search and rescue mission if the plan locates the sought after object or person.

After completion of the flight mission, or in response to a rerouting request received by the UAV, the UAV is received in the UAV pod and the flight survey data is provided to UAV pod memory (block 612). In an alternative embodiment, rather than returning to the original UAV pod, the UAV flies to and is received by a second UAV pod (block 614). Such an alternative embodiment may be utilized in order to transition the UAV into an adjacent geographic survey region for receipt of a new plurality of missions for a second geographic survey. Alternatively, such an embodiment may be used to provide for an extended geographic area survey, one that would ordinarily not be accomplished with a single UAV due to the UAVs inherent power/range limitation. If all missions in the plurality of missions have not yet been completed (block 616), then the next one of the plurality of missions is provided to the UAV (block 608) and the UAV is again launched out of the UAV pod autonomously (i.e., without human intervention) to perform the next survey flight mission and the UAV may return to the UAV pod after completing the flight mission and the recorded survey data provided to the UAV pod. Otherwise, if all missions are completed (block 616), then the completed flight survey data may be provided from the UAV pod (block 618). The survey data may be provided to UAV pod memory that is in the form of detachable memory in the UAV pod, such as SD cards, USB flash memory, or otherwise detachable and portable memory, to a UAV pod servicer, or may be provided wirelessly through a cell phone connection, WLAN or LAN connection, or satellite-enabled transceiver. In an alternative embodiment, the UAV is routed to a LAN area for the LAN to receive the flight survey data wirelessly during flight and before returning for landing in the UAV pod (block 619).

As shown in FIG. 6, the UAV pod (which may now include the UAV) may then be retrieved and returned to an operations support center (block 620). A second plurality of flight missions may then be uploaded into the UAV pod to accomplish a second data request from the same or a different customer and the UAV pod re-deployed. In an alternative embodiment, rather than returning the UAV pod to a support center, the UAV pod may be moved or migrated (block 622) to a second or next geographic coverage area for further use.

In a further alternative embodiment, the UAV pod may be deployed to a launch site prior to providing the UAV pod with flight missions data representing the planned flight missions. In such a scheme, the UAV pod may establish or join a local LAN connection for receipt of the planned flight missions on-site.

FIG. 7 shows a pod 700 that due to its rural location lacks a wireless data connection and the UAV 702 has flown from its pod 700 to loiter above a house 703 to be within range of the house's Wi-Fi connection. This allows the UAV 702 to download data to either a server at the house 703 or to another location via an Internet connection. The UAV 702 can either store the data on board and then transmit it via the Wi-Fi connection or relay a signal from the pod 700 to the Wi-Fi. FIG. 7 also shows that the UAV 702 could also transmit information by means of a physical act, such as loitering over an event of interest determined by the prior collection and processing of data. One example of such an event of interest could be the location of a lost person 704 or the location of an area of farmland that may need additional water.

The flight survey data provided to UAV pod memory (perhaps detachable memory), provided wirelessly from the UAV pod 700, or even provided to a local LAN as described above, may be in raw or pre-processed form. For example, the flight survey data may simply be “zipped” and relayed to a remote processing station where all of the data is processed. Pre-processing the flight survey data prior to providing such from the UAV pod 700 or directly from the UAV 702 provides advantages. Data transmission bandwidth requirements may be reduced from what would otherwise be needed to transmit raw data for processing to an operational support center. A reduction in transmission bandwidth requirements may translate into reduced data transmission costs and time. In a preferred embodiment, either the UAV processor 208 (see FIG. 2) or UAV pod processor 114 (see FIG. 1) may pre-process the UAV-captured raw data (e.g., block 618, see FIG. 6). The UAV-captured raw data such as camera imagery, event logs, GPS and IMU raw data may be converted into viewable JPGs with accompanying geospatial location (i.e., “geo-tagging”) for transmission. However, additional pre-processing may be performed either by the UAV processor or UAV pod processor. For example, the JPG images and accompanying geospatial location may be further processed to stitch the images into an orthomosaic so that what is sent from the UAV pod or from the UAV itself is a single high resolution image covering the entire flight survey area (or from an individual flight mission) resulting in the lowest bandwidth needed for transmission and the highest level of automation of pre-processing for the ultimate customer for measuring roads, buildings, fields, identifying agricultural progress, inspecting infrastructure, urban planning, and other analysis.

As shown in FIG. 7, the UAV pod 700 may include an interface and display 705 to provide the collected data and processed data for use at site without the need for transmission from the pod 700 to an offsite location. For example the display 705 may be used to inform local users (e.g., farmhands) of areas that need additional watering or the like.

Local UAV Operation

FIG. 8 is a flow diagram illustrating one embodiment of a method of conducting flight missions for the UAV. The UAV may be transmitted or otherwise provided with one of the plurality of missions (block 800) that reside in the UAV pod. The UAV may be launched vertically out of the UAV pod (block 802), preferably under its own power using the two rotors on the UAV. In one embodiment, the immediate environment over the UAV pod is monitored for obstacles and weather (block 804) that may otherwise interfere with launch of the UAV. In such an embodiment, if no obstructions are detected (block 806), then the UAV may be launched out of the UAV pod (block 802). Otherwise, launch of the UAV is delayed or cancelled and the UAV pod continues to monitor for overhead obstacles and weather (block 804, 806), as well as the UAV battery status (block 810). After launch, the UAV pod may monitor the UAV's trajectory (block 808) for comparison to the planned flight mission trajectory and for correction thereof. If UAV battery power is low or otherwise drops below a predetermined voltage threshold (block 812), then the UAV pod may provide rerouting instructions to the UAV (block 814) to shorten the current mission to enable a safe return of the UAV to the UAV pod. In an alternative embodiment, the UAV is directed to return immediately to the UAV pod (block 816) or to an intermediate pre-determined position. If, however, the battery is not low (block 812), and no other flight warning condition is triggered (block 818) the mission continues (block 820). If the current UAV mission has been completed (block 820), the UAV returns to the UAV pod (block 816) for landing and the geographic survey data is downloaded to the UAV pod memory (block 822) such as by a wireless or wired transfer of the mission data to the UAV pod memory. The UAV pod protective cover may be closed (block 824) to protect the UAV from the external environment (i.e., rain, direct sun, vandals, or damaging particulate matter).

Methods of General Survey Use—Contiguous Survey Areas

While embodiments of the system thus far are described within the context of a flight survey using only one UAV pod, it is contemplated that a customer of the system may request a geographic coverage area that extends beyond the capabilities of a single UAV and UAV pod combination. FIG. 9 is a block diagram illustrating the use of a plurality of UAV pods with only one UAV to extend the possible geographic survey area from what would otherwise exist with only one UAV. An operator of the system may review the customer request and allocate n number of UAV pods for deployment at a given UAV pod spacing. An extended geographic survey area 900 may thus be divided into a plurality of individual geographic survey areas 902 for mission planning purposes. A respective plurality of UAV pods (each indicated by an ‘X’) may be deployed in predetermined launch locations so as to substantially cover the extended geographic survey area 900 and a communication network established to allow a single human manager to monitor the setup of the entire network of UAV pods. The size of each coverage or survey area 902 and the positioning of the pods across the area 900, may vary by a variety of factors including the range, flight time, recharge time, sensor or sensors of the UAV to be employed in that area 902, the frequency of the survey, the weather or season (as they may affect performance of the UAV and/or the charging capabilities of the pod), obstacles and obstructions, wireless communications between the pod and either the UAV, other pods, cellular network, or other radio system, dispersion of other pods in adjacent areas, and the like. The positioning of the pods may also be affected by the ability to position or deliver the pods to desired locations given the accessibility provided by local roads and terrain. A UAV pod 904 having a pre-loaded UAV may be deployed having a plurality of preloaded missions that are collectively sufficient to survey the immediately-surrounding coverage area 906. After the UAV has autonomously completed the missions to survey the immediately-surrounding coverage area 906, the UAV 908 may be transitioned to the next predetermined UAV pod 910 for recharging (or refueling) and to receive the first of a next plurality of flight missions to cover the second immediately-surrounding coverage area 912. Through the use of a plurality of missions designed specifically to collectively cover the second coverage area 912, the UAV may then migrate to the next coverage area 914 and so on until the entire extended coverage area 900 has been surveyed. In one embodiment, a non-coverage area 916, such as a lake, mountain, forest, city, non-farm land, or other area that is not of interest, is included in the extended coverage area 900 and may be avoided from survey activities to possibly extend the serviceable area for the UAV.

In an alternative embodiment that recognizes the autonomous landing capability of the UAV, the UAV, rather than transitioning to the next individual geographic survey area 902 or to the next individual geographic survey areas 902, the UAV may fly to a predetermined data offloading waypoint, such as a customer's farm house or automobile, to establish or join a local LAN connection or to establish a wireless connection to provide a data dump of geographic survey data, such as that shown in FIG. 7, to an operations center disposed remote from the UAV pod.

In a further alternative embodiment, more than one UAV may be provided within the extended geographic survey area 900, with each UAV having a different sensor suite to gather complementary data for the customer. In such a scheme, each UAV may survey the entire extended geographic survey area 900 by transitioning through the plurality of individual geographic survey areas 902 over time, or to only a subset of each area 900, to obtain a more complete understanding of the area 900 than would be possible with only a single UAV sensor suite.

Also, although the prior description describes one UAV for each UAV pod, in an alternative embodiment, each UAV pod may selectively encompass, provide power for, and distribute missions to two or more VTOL UAVs. In some embodiments, each pod deployed to a survey area 902 will include its own UAV to allow the given area 902 to be surveyed at the same time, or about the same, time or frequency as any other area 902. UAV pods in different areas 902 could contain UAVs with different sensors, or sensor suites, and the UAV pods could trade UAVs as necessary to obtain the desired sensor coverage.

Although FIG. 9 illustrates each immediately-surrounding coverage area (e.g., 906, 912, 914) as being circular, a UAV pod and associated UAV may be provided with a plurality of missions that cover a rectangular coverage area 1000 (see FIG. 10) or a coverage area having different regular or irregular shapes to accomplish the overall goal of surveying an extended coverage area 1002 that could not otherwise be covered without the use of multiple UAVs or with UAVs having significantly greater range capabilities, as illustrated in FIG. 10.

Methods of General Survey Use—Non-Contiguous Survey Areas

FIG. 11 illustrates two extended coverage survey areas that may be serviced using only one UAV or a limited number of UAVs. The two extended coverage survey areas (1102, 1104) are not contiguous, but rather are separated into two distinct extended coverage areas. During a mission planning procedure, each of the two extended coverage survey areas (1102, 1104) are broken up into area sets 1106 that are serviceable with a single UAV/UAV pod set. In such an arrangement, a single UAV may transition from one area set 1106 to the next within the first extended coverage survey area 1102 as the respective missions are completed, until transitioning to the next extended coverage survey area 1104.

While various embodiments of the invention have been described, it will be apparent to those of ordinary skill in the art that many more embodiments and implementations are possible that are within the scope of this invention. 

We claim:
 1. An unmanned aerial vehicle (UAV) storage and launch system, comprising: a UAV pod processor; a proximity sensor coupled to a UAV pod, wherein the proximity sensor is configured to detect the presence of an object positioned over the UAV pod; a UAV pod transceiver in communication with the UAV pod processor, the UAV pod processor configured to: enable a no-go flight decision based on the detected presence of an object positioned over the UAV pod; enabling a go flight decision based on no detected presence of an object positioned over the UAV pod; monitor a winged two-rotor UAV trajectory, wherein the wings provide a primary source of lift during horizontal flight of a UAV; compare the monitored UAV trajectory to mission instructions for the UAV, wherein the mission instructions comprise a UAV trajectory; provide navigation instructions to the UAV processor for correction of the UAV trajectory to the provided mission instructions in response to the compared monitored UAV trajectory and mission instructions, wherein the provided mission instructions are not modified; provide navigation instructions to the UAV processor to fly the UAV to a predetermined data offloading waypoint to provide a transfer of geographic survey data based on the provided mission instructions; monitor a UAV battery status; and a UAV pod memory in communication with the UAV pod processor, the UAV pod memory storing a plurality of UAV missions that collectively provide the geographic survey data of an area.
 2. The system of claim 1, wherein the UAV pod processor is configured to monitor for overhead obstacles using a proximity sensor in communication with the UAV pod processor.
 3. The system of claim 1, wherein the UAV pod processor is configured to monitor the weather using a weather sensor.
 4. The system of claim 1, further comprising: a long-range UAV pod transceiver coupled to the UAV pod and in communication with the UAV pod processor.
 5. An unmanned aerial vehicle (UAV) storage and launch system, comprising: a UAV pod having a UAV pod processor and short-range UAV pod transceiver; a proximity sensor coupled to the UAV pod, wherein the proximity sensor is configured to detect the presence of an object positioned over the UAV pod, when an object is present, wherein the UAV pod processor enables a no-go flight decision based on the detected presence of an object positioned over the UAV pod, and wherein the UAV pod processor enables a go flight decision based on no detected presence of an object positioned over the UAV pod; a winged vertical takeoff and landing (VTOL) two-rotor UAV capable of being enclosed in the UAV pod, the two-rotor UAV having a UAV processor and a UAV transceiver, the UAV processor in communication with the UAV pod processor through the short-range UAV pod transceiver and the UAV transceiver, wherein the wings provide a primary source of lift during horizontal flight of the UAV; and wherein the UAV pod processor is configured to: provide mission instructions to the UAV processor, wherein the mission instructions comprise a UAV trajectory; monitor the UAV trajectory; compare the provided mission instructions to the monitored UAV trajectory; provide navigation instructions to the UAV processor for correction of the UAV trajectory to the provided mission instructions in response to the compared mission instructions and UAV trajectory, wherein the provided mission instructions are not modified; and provide navigation instructions to the UAV processor to fly the UAV to a predetermined data offloading waypoint to provide a transfer of geographic survey data based on the provided mission instructions.
 6. The system of claim 5, wherein the UAV pod processor is further configured to provide reroute instructions to the two-rotor UAV.
 7. The system of claim 6, wherein the rerouting instructions include instructions to return to the UAV pod for landing.
 8. The system of claim 5, further comprising: a weather sensor in communication with the UAV pod processor; and a UAV pod memory in communication with the UAV pod processor.
 9. The system of claim 8, wherein the UAV pod memory is portable memory.
 10. The system of claim 8, further comprising: a long-range UAV pod transceiver coupled to the UAV pod and in communication with the UAV pod processor.
 11. The system of claim 10, wherein the UAV pod processor is further configured to monitor UAV pod external environmental conditions in response to information received from the weather sensor.
 12. The system of claim 5, further comprising: a UAV pod cover operable to open and close.
 13. A method of unmanned aerial vehicle (UAV) launch and control, comprising: transmitting one of a plurality of mission instructions to a winged two-rotor UAV, wherein the transmitted mission instructions comprises a UAV trajectory, wherein the two-rotor UAV comprises a UAV processor, and wherein the wings provide a primary source of lift during horizontal flight of the UAV; detecting a presence of an object positioned over a UAV pod by a proximity sensor coupled to the UAV pod wherein the proximity sensor is configured to detect the presence of an object positioned over the UAV pod, when an object is present; enabling a no-go flight decision from a UAV pod processor based on the detected presence of an object positioned over the UAV pod; enabling a go flight decision from the UAV pod processor based on no detected presence of an object positioned over the UAV pod; launching the two-rotor UAV from the UAV pod if the go flight decision is enabled by the UAV pod processor; monitoring the UAV trajectory of the two-rotor UAV using a transceiver in communication with a processor; comparing the transmitted mission instructions to the monitored trajectory of the UAV with the processor; providing navigation instructions to the UAV processor with the transceiver for correction of the UAV trajectory to the transmitted mission instructions in response to the compared mission instructions and UAV trajectory, wherein the provided mission instructions are not modified; and providing navigation instructions to the UAV processor to fly the UAV to a predetermined data offloading waypoint to provide a transfer of geographic survey data based on the provided mission instructions.
 14. The method of claim 13, further comprising: downloading geographic survey data from the two-rotor UAV to a memory in communication with the UAV processor.
 15. The method of claim 14, wherein the memory comprises portable memory detachably connected.
 16. The method of claim 13, further comprising: monitoring a battery status of the two-rotor UAV during flight; and providing re-routing instructions to the two-rotor UAV from the processor.
 17. The method of claim 16, wherein the step of providing re-routing instructions is performed in response to receipt of UAV battery status data in the processor.
 18. The method of claim 17, wherein the providing re-routing instructions includes UAV instructions to land.
 19. The method of claim 13, further comprising: landing the two-rotor UAV in the UAV pod; closing a UAV pod protective cover over the two-rotor UAV; downloading geographic survey data from the two-rotor UAV to a UAV pod memory in communication with the UAV processor; transmitting another one of a plurality of missions instructions to the two-rotor UAV seated in the UAV pod; opening the protective cover; and launching the two-rotor UAV out of the UAV pod.
 20. The method of claim 19, further comprising: monitoring the weather using a weather sensor.
 21. The method of claim 19, further comprising: transmitting the geographic survey data to an operations center disposed remote from the UAV pod.
 22. The method of claim 19, further comprising: monitoring for overhead obstacles using a proximity sensor. 